Card dispenser

ABSTRACT

A card dispenser for dispensing a rewritable card is disclosed herein. The card dispenser may include a card feeder for receiving or dispensing a rewritable card. In addition, the card dispenser includes a roller assembly for moving the card from the card feeder to components within the card dispenser; a processor for receiving card data via a short-range wireless connection with a mobile device of a user, the card data including (i) a card identifier of a plurality of card identifiers associated with an account of the user and (ii) a unique derivation key for encrypting the card identifier; and a card writer for powering an electrophoretic display of the card, causing at least a portion of the card data to be rendered on the display, and stopping the powering of the display.

BACKGROUND

Card systems have been used in many industries. For example, the hotelindustry uses card systems to assign key cards to hotel rooms to enablecustomers to open hotel rooms using key cards instead of using keys.Once the customer has checked out of the room, the key card can bereassigned to another room. Furthermore, financial institutions use cardsystems to generate bank cards, credit cards, and other cards to enablecustomers to interact with their accounts. Some card systems include theability to create temporary cards that are valid only under specificconditions (e.g., for a given period of time). Card providers may usecard printers at their premises to create the required cards. Cardprinters generally process new cards. The processing of the new card mayinclude printing on a surface of the card. Thus, to acquire a temporarycard, a customer is generally required to contact the card provider, andthe card provider may issue a temporary/new card to the customer in thesame manner as a regular card is issued. In many situations, thecustomer must go through various people and wait for a prolonged periodof time (e.g., 7-10 days) before the card is received and maybe used.This may not be acceptable to the customer and the customer may useother means to perform the task that the card performs.

SUMMARY

In some embodiments, to solve this problem, methods, apparatuses, and/ora self-service card dispenser system are disclosed herein that enable acard dispenser to communicate with a device of a user to dispense a cardassociated with an account of the user. That is, upon request, based onthe data received from the device of the user, a card dispensergenerates and dispenses, to the user, a card associated with the user'suser account.

In some embodiments, the card dispenser may detect a device of a user(e.g., via a short-range wireless connection) and receive, from thatdevice, card data for printing information onto a card received in thecard dispenser. The device of the user may have an installed applicationthat interfaces with the systems of the card provider. The applicationmay store account information associated with the account of the usercorresponding to the card provider. For example, if a card provider is ahotel, the application may be interfacing with the hotel's computersystems (e.g., servers) that store user account information. Thus, theapplication may request and/or store account information associated withthe particular user.

A user may insert a card into a device associated with the carddispenser (e.g., a user may reuse a card in the user's possession), orthe card may be inserted into the card dispenser by a device coupledwith the card dispenser (e.g., a new card may be dispensed to the user).The user may select an option within the application for generating anew or temporary card. For example, the user may want to generate atemporary credit card for credit card transactions or a hotel card forbeing able to enter the hotel and open a hotel door. When the device ofthe user receives the selection, appropriate card data may be receivedat the user device from, for example, the server(s) of the cardprovider. When the card data is received at the device of the user, thecard data may be transmitted to the card dispenser. The card data (e.g.,received from the device of the user) may include (i) a card identifierassociated with an account of a user and (ii) an encryption key forencrypting the card identifier. As an example, the encryption key may bea unique derivation key for encrypting the card identifier, where thekey is derived from a unique master key (e.g., associated with the useraccount). Furthermore, the card data may include a plurality of cardidentifiers associated with the account of the user. Each identifier maybe received along with a unique derivation key for encrypting the cardidentifier.

The card dispenser may power an electrophoretic display of the card,overwrite the card data on a memory of the card, and cause at least aportion of the card data to be rendered on the display of the card. Thecard dispenser may stop the powering of the display, subsequent towhich, rendering of the portion of the card data remains on the displayof the card. At this point, the card may be dispensed to the user. Thus,the card dispenser performing these actions may be a part of aself-service process where a user may receive a card (e.g., a temporarycard or a new card).

In some embodiments, the card dispenser may include a card feeder forreceiving or dispensing the card; a roller assembly for moving the cardfrom the card feeder to one or more components within the card dispenserand back to the card feeder; and a card writer for overwriting thememory of the card with the card data.

Various other aspects, features, and advantages of the invention will beapparent through the detailed description of the invention and thedrawings attached hereto. It is also to be understood that both theforegoing general description and the following detailed description areexamples and not restrictive of the scope of the invention. As used inthe specification and in the claims, the singular forms of “a,” “an,”and “the” include plural referents unless the context clearly dictatesotherwise. In addition, as used in the specification and the claims, theterm “or” means “and/or” unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of card dispenser for dispensing a card, inaccordance with one or more embodiments.

FIG. 2 shows an example of a system including a card dispenser, inaccordance with one or more embodiments.

FIGS. 3-5 show flowcharts of methods of dispensing a card, in accordancewith various embodiments.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the embodiments of the invention. It will beappreciated, however, by those having skill in the art that theembodiments of the invention may be practiced without these specificdetails or with an equivalent arrangement. In other cases, well-knownstructures and devices are shown in block diagram form in order to avoidunnecessarily obscuring the embodiments of the invention.

FIG. 1 shows an example of a card dispenser 100, in accordance with oneor more embodiments. Card dispenser 100 may be configured to receive acard at an input area, write a card identifier or other card data to thecard, and dispense the card after writing the card data to the card. Asan example, the card data may include (i) one or more card identifiersassociated with a user account (e.g., one or more virtual card numbersassociated with the user account), (ii) one or more encryption keys forencrypting one or more pieces of the card data (e.g., unique derivationkeys or other keys for encrypting the card identifiers or other data),(iii) one or more card use parameters (e.g., parameters defining one ormore restrictions or other features of the card related to usage of thecard), or (iv) other data.

As shown in FIG. 1 , in some embodiments, card dispenser 100 may includecard feeder 110, transport assembly 140, card writer 150, controller170, or other components. Some or all components of the card dispenser100 may be operatively coupled and included in an enclosure (not shown).In some embodiments, some or all components of the card dispenser arenot collocated (e.g., are not within a same enclosure, or in a samephysical location). Card dispenser 100 may be configured to receive acard 190. Card 190 may be moved within components of card dispenser 100,where it is processed and dispensed. As an example, the processing mayinclude communicating with computing components on the card. Forexample, some cards include microchips that are able to storeinformation including a card number (e.g., an encrypted card number) aswell as other identifying information. In addition, the processing mayinclude an authenticating process so that unauthorized car dispensersystems are not able to overwrite data on cards. In some embodiments,the authenticating process may be mutual so that unauthorized cards arenot able to gain access to the provider's system. The authenticatingprocess may use public/private key infrastructure (PKI) or anothersuitable authenticating process.

In some embodiments, the card may include a rewritable memory area forstoring data that can be retrieved or otherwise read. For example, thecard may include an electrophoretic display that will hold a staticimage, even without electricity—when there is no change in image ortext, the electrophoretic display presents the last content uploaded andwill hold it in perpetuity. The electrophoretic display may consumepower only when the content on it is changing. Thus, the electrophoreticdisplay is extremely energy efficient and may be capable of running formonths on a single battery charge. The card dispenser may store carddata on the card and render a portion of the card data on theelectrophoretic display of the card.

In some embodiments, card 190 may include circuitry 195, a display 198,or other components. Circuitry 195 may provide information processingand communications capabilities within card 190, or between card 190 andcard dispenser 100 or other systems (e.g., server system 250, orpoint-of-sale terminal 290 described herein). Card dispenser 100 may beconfigured to receive card 190 and power circuitry 195. For example,circuitry 195 may be powered by contact with the card dispenser (e.g.,electrical connection between the circuitry and card dispenser). Inanother example, circuitry 195 may be wirelessly powered withoutphysical contact with the card dispenser (e.g., via antennas ofcircuitry 195 and radio frequency signals from card dispenser 100,powering via inductive coupling, etc.).

Circuitry 195 may include a processor, a memory, or other components.For example, card data received by card dispenser 100 may be stored inthe memory of circuitry 195, and a portion of the card data may berendered on display 198. In some embodiments, circuitry 195 may beembedded in card 190. In some embodiments, circuitry 195 may include amicrochip, a magnetic strip, a barcode, Quick Response (QR) code, anRFID tag, a communication device (e.g., Near Field Communication (NFC)antenna, Bluetooth® device, or WiFi device), or other electroniccomponents.

Card dispenser 100 may communicate with circuitry 195 to authenticatethe card or the user. As an example, after receiving the card, carddispenser 100 may request authentication of the card before processingthe card (e.g., storing information, rendering information, etc.). Insome embodiments, circuitry 195 may generate a cryptogram from securitydata previously encoded in circuitry 195 (e.g., by the card issuer), andsend the cryptogram along with a digital certificate (from the issuer)to the card dispenser for verification of authenticity of the card bythe card dispenser.

Card dispenser 100 may be configured to authenticate the user in variousways. For example, card dispenser 100 may use multi-factorauthentication, PKI, or another suitable authentication method. In someembodiments, card dispenser may authenticate the card or the user usingproximity of a user device (e.g., a mobile phone). That said, othermethods of authenticating the card by the card dispenser 100, or theuser are contemplated within the scope of the present disclosure.

Circuitry 195 may be configured to store card data received by carddispenser 100. In some embodiments, card dispenser 100 may read previousinformation that was previously stored on circuitry 195 (e.g., in thecase of a card that is being re-used) before storing the card data. Forexample, card dispenser 100 may be configured to overwrite the previousinformation, keep all the previous information and add the card data, orkeep some of the previous information and add the card data.Furthermore, card dispenser 100 may be configured to determine whatinformation to keep and what information to overwrite (e.g., bycomparing the previous information and the card data). For example, theprevious information may include generic information about the cardissuer, contact information, instructions for basic function ofcircuitry 195, or other generic information, that the card dispenser maydetermine not to overwrite.

In some embodiments, card data received by card dispenser 100 and storedon circuitry 195 may include a card identifier associated with anaccount of the user. The card identifier may be used to authenticate thecard (e.g., after it is dispensed by the card dispenser 100). The carddata may include a unique derivation key for encrypting the cardidentifier. For example, the unique derivation key may be derived from aunique master key (e.g., of the issuer, associated with the useraccount, etc.). Furthermore, the card data may include a plurality ofcard identifiers associated with the account of the user. Eachidentifier may be received along with a unique derivation key forencrypting each card identifier. In addition, card data stored incircuitry 195 may include other security information that may allow thecard to be securely used after its dispensed from card dispenser 100.For example, card data may include applications, programs, requirements,or instructions from the card issuer for generating session keys andcryptograms that are unique to the card 190 to be used duringtransactions (e.g., for authentication or authorization of transactionswith the card issuer).

In some embodiments, card data received by card dispenser 100 and storedon circuitry 195 may include one or more card use parameters that defineusage of the card after the card dispensed by card dispenser 100. Inaddition, the card use parameters may be determined by the user, thecard issuer, or the card dispenser. Furthermore, the card data mayinclude a plurality of card identifiers that are each associated with ause parameter. For example, the use parameter may define one or moretime periods during which use of the card is permitted or prohibited,locations at which use of the card is permitted or prohibited, servicesor users for or by which use of the card is permitted or prohibited, orother restrictions or use parameters for using the card. In someembodiments, the card use parameters may be defined by the user (e.g.,using a user device). As an example, the card use parameters may bedefined by an application residing on the user device. For example, whenthe application on the user device receives a request for dispensing anew card, the application may transmit a request to a card provider(e.g., to one or more servers at the card provider) for data forgenerating new/temporary card. The user device may receive the card dataalong with the card use parameters.

In some embodiments, the card use parameters stored in circuitry 195 mayinclude an expiration date, a location (e.g., a specific building,floor, garage, office, lab, etc.), a geographic area (e.g., a specificcity, state, country, etc.), a type of business where the card is valid,or other use parameters. The use parameter(s) may be determined by theuser (e.g., via a user interface of the user device or the userinterface of the card dispenser), by the issuing entity, or anotherentity. For example, the issuing entity may be a government entity, anemployer, a business, a financial institution, or another suitableissuing entity. The cards dispensed by card dispenser 100 may be usedfor different purposes. For example, the cards may be ID cards,transactional cards, credit cards, bank cards, phone cards, passports,driver's licenses, network access cards, employee badges, securitycards, visas, immigration documentation, citizenship cards, socialsecurity cards, security badges, gift cards, or other types of cards.

In some embodiments, a portion of the card data received by carddispenser 100 and stored in circuitry 195 may be rendered on the card.For example, a portion of the data may be rendered on display 198, andanother portion may be rendered on the surface of the card in adifferent manner (e.g., printed on the card). In some embodiments, thecard dispenser 100 may determine the portion to be rendered on thedisplay based on the type of display, size of the display, or otherfeatures of the display. Card dispenser 100 may receive instructionsindicating which portion of the card data should be rendered on thedisplay (e.g., from server system 250 or from the user).

In some embodiments, card dispenser 100 may be configured to overwriteprevious display information, keep all the previous display informationand add a portion of the card data, or keep some of the previous displayinformation and add a portion of the card data. Card dispenser 100 maybe configured to determine which information to keep and whichinformation to overwrite (e.g., by comparing the previous displayinformation and the card data). For example, the previous displayinformation may include generic information about the card issuer,contact information, card holder, or other generic information, that thecard dispenser may determine to keep.

In one example, card dispenser 100 may be configured to power display198, render the portion of the card data on the display, and power thedisplay off such that the portion of the data remains on the displayafter the power is turned off. For example, display 198 may be anelectrophoretic display configured to display the portion of the datawithout requiring power. In some embodiments, the portion of the carddata may remain on the display until it is overwritten (e.g., by carddispenser 100).

In another example, card dispenser 100 may be configured to powerdisplay 198, render a portion of the card data on the display, and powerthe display off such that the portion of the data does not remain on thedisplay after the power is turned off. In some embodiments, the data ispresented back on the display responsive to the circuit 195/display 198being powered on. For example, circuit 195 may be turned on responsiveto the card being in proximity of a user's device, point-of-saleterminal 290, or the card dispenser 100 (e.g., using radio frequency).The card may be then authenticated (e.g., via multiple-factorauthentication), after which the display is turned on and the data ispresented on the display.

In some embodiments, card dispenser 100 may be configured to render dataon the surface of the card. For example, a portion of the card data maybe printed on one or more outer surfaces of the card. This action may beperformed using one or more card printing techniques, including thermaltransfer using color ribbons, dye diffusion thermal transfer, laserprinting, ink jet, reverse image transfer techniques, stamping,embossing, water mark techniques, or other printing (or writing)techniques. In some embodiments, card dispenser 100 may determine anappropriate technology for different types of data to be printed.Furthermore, card dispenser 100 may be configured to overwrite or erasesome or all previously printed information. Card dispenser 100 may alsobe configured to determine which printed information to keep and whichinformation to overwrite (e.g., by comparing the previously printedinformation and the card data).

In some embodiments, card dispenser may include card feeder 110 forreceiving the card and feeding the card into card dispenser 100. Cardfeeder 110 may be operatively connected to transport assembly 140 fortransporting cards within card dispenser 100. Card feeder 110 may beconfigured to dispense the card. For example, after processing by carddispenser 100, a card may be transported back to card feeder 110 fordispensing. In some embodiments, card feeder 110 may be configured forreading information from the card (e.g., via a card reader in the cardfeeder 110). Furthermore, card feeder 110 may be configured to powercircuitry 195 of the card (e.g., by electrical connection between thecircuitry and card dispenser, or via antennas of circuitry 195 and radiofrequency signals from card feeder 110). In some embodiments, cardfeeder 110 may communicate with circuitry 195 to authenticate the cardor the user. As an example, after receiving the card, card feeder 110may request authentication of the card before processing the card (e.g.,storing information, rendering information, etc.). In response to theauthentication request, circuitry 195 may generate a cryptogram fromsecurity data previously encoded in circuitry 195 (e.g., by the cardissuer), and send the cryptogram along with a digital certificate (fromthe issuer) to card feeder 110 for verification of authenticity of thecard by the card feeder 110. In addition, card dispenser 100 may beconfigured to authenticate the card or the user (e.g., via multi-factorauthentication, proximity of a user device, etc.).

In some embodiments, the card feeder 110 may be in the form of a cardslot, a card tray, or another card receptacle for receiving a card andproviding the card to the card dispenser 100 for further processing.Card dispenser 100 may include a card supply storage 120 for storing andsupplying one or more cards to be processed by card dispenser 100. Insome embodiments, card supply storage 120 may be operatively connectedto card feeder 110 or to transport assembly 140 for transporting cardswithin card dispenser 100. In addition, card supply storage 120 maystore “blank” cards that have not been used before or have generic or nodata on them. For example, responsive to a request for a new card ininstances where a card is not provided through card feeder 110, a cardis supplied from card supply storage 120. In some embodiments, cardsupply storage 120 may be in the form of a tray, a cassette, areceptacle, or another type of card storage for holding cards. Cardsupply storage 120 may include a card pusher, a loaded spring, clamps,suction cups, or other mechanisms for moving a card from card supplystorage 120 to transport assembly 140.

In some embodiments, transport assembly 140 may be configured to movecard 190 from card feeder 110 or card supply storage 120 to one or morecomponents within card dispenser 100. The transport assembly 140 may beconfigured to move the card back to card feeder 110 (e.g., afterprocessing by card dispenser 100). Transport assembly 140 may beoperatively connected to one or more components of card dispenser 100(e.g., card feeder 110, card supply storage 120, card writer 150, cardoutput 160, controller 170, or other components). In some embodiments,transport assembly 140 may include a roller assembly, movingreceptacles, belts, pulleys, or other transport mechanisms for movingthe card within the card dispenser 100.

Card writer 150 may be configured to receive a card from card feeder 110or card supply storage 120 via transport assembly 140 and store orrender card data (received by card dispenser 100). For example, cardwriter 150 may be configured to receive card data to be written on thecard. Card writer 150 may receive the card data in a variety of ways.For example, card data may be received from server system 250 (shown inFIG. 2 and described herein). In another example, card data may bereceived via a user device of the user (e.g., mobile device). In yetanother example, card data may be received from the user device usingradio frequency, Near Field Communication (NFC), Bluetooth®, WiFi, orother contactless manner. In some embodiments, card data may be receivedby controller 170 and transmitted to card writer 150.

Card writer 150 may be configured to receive card 190 and powercircuitry 195. In some embodiments, card writer 150 may power circuitry195 by contact with the card (e.g., electrical connection between thecircuitry 195 and card writer 150). While in some embodiments, cardwriter 150 may power circuitry 195 without physical contact with thecircuitry (e.g., radio frequency signals from card writer 150 andantennas of circuitry 195). Card writer 150 may be configured to storeinformation (card data) in card circuitry 195 in a logical manner. Forexample, on a microchip, a magnetic strip, a barcode, Quick Response(QR) code, an RFID tag, or another component or components of circuitry195 of the card. In some embodiments, card writer 150 may use differenttechniques to write (store) data in circuitry 195 of the card. Forexample, in some cases, card writer 150 may include a conductive platefor transferring information to and from circuitry 195. In someembodiments, the card writer 150 may be configured to transferinformation in a contactless manner (e.g., by using radio frequency,Near Field Communication (NFC), Bluetooth®, WiFi, or other contactlessmanner). Furthermore, card writer 150 may be configured to encodeinformation onto a magnetic stripe of the card (e.g., by modifyingmagnetism of iron-based magnetic particles). That said, other techniquesfor transferring data from card writer to the card circuitry arecontemplated within the scope of the disclosure.

In some embodiments, card writer 150 may communicate with circuitry 195to authenticate the card 190 or the user. As an example, after receivingthe card, card writer 150 may request authentication of the card beforetransferring or rendering data. For example, card writer 150 may readprevious information that was previously stored in circuitry 195 (e.g.,in the case of a card that is being re-used) before storing the carddata, and may overwrite the previous information, keep all the previousinformation and add the card data, or keep some of the previousinformation and add the card data. In some embodiments, card writer 150may be configured to determine which information to keep and whichinformation to overwrite (e.g., by comparing the previous informationand the card data). For example, the previous information may includegeneric information about the card issuer, contact information,instructions for basic function of circuitry 195, or other genericinformation, that card writer may determine to keep, while determiningto overwrite previous account information (e.g., because the previousaccount information is associated with a previous user).

In some embodiments, card writer 150 may be configured to store (e.g.,in circuitry 195 of card 190) card data that includes a card identifierassociated with an account of the user, a unique derivation key forencrypting the card identifier, applications, programs, requirements, orinstructions from the card issuer for generating session keys andcryptograms that are unique to card 190 (e.g., for authentication orauthorization of transactions with the card issuer). Furthermore, cardwriter 150 may be configured to store one or more card use parameters onthe card (e.g., parameters that define usage of the card after the cardis dispensed by card dispenser 100). In some embodiments, card writer150 may be configured to store the card use parameters that define time,location, services, users, restrictions, or other parameters for usingthe card. For example, the card use parameters may include an expirationdate, a location (e.g., a specific building, floor, garage, office, lab,etc.), a geographic area (e.g., a specific city, state, country, etc.),a type of business where the plastic is valid, or other use parameter.

In some embodiments, card writer 150 may be configured to cause aportion of the card data received by card dispenser 100 and stored incircuitry 195 to be rendered on the card 190. For example, card writer150 may be configured to program the card 190 so that the card 190 isprogrammed to render a portion of the data on display 198. Additionallyor alternatively, card writer 150 may render the portion of the data onanother portion on the surface of the card in a different manner (e.g.,printed on the card 190). In some embodiments, card writer 150 maydetermine the portion of data to be rendered on the display based on thetype of display, size of the display, or other features of the display.For example, card writer 150 may receive instructions indicating whichportion of the card data is to be rendered on the display (e.g., fromserver system 250 or from the user). In some embodiments, card writer150 may be configured to overwrite previous display information, keepall the previous display information and add a portion of the card data,or keep some of the previous display information and add a portion ofthe card data. Card writer 150 may be configured to determine whichinformation to keep and which information to overwrite (e.g., bycomparing the previous display information and the card data). Forexample, the previous display information may include genericinformation about the card issuer, contact information, card holder, orother generic information, that the card writer 150 may determine tokeep.

In some embodiments, card writer 150 may be configured to power display198, render the portion of the card data on the display, and power offthe display such that the portion of the data remains on the displayafter the power is turned off. For example, display 198 may be anelectrophoretic display configured to display at least a portion of thecard data without requiring power. In some embodiments, the portion ofthe card data may remain on the display until that data is overwritten(e.g., by card writer 150).

In some embodiments, card writer 150 may be configured to power display198, render a portion of the card data on the display, and power off thedisplay such that the portion of the data does not remain on the displayafter the power is turned off. For example, the data may be presentedback on the display responsive to circuitry 195/display 198 beingpowered on. In another example, responsive to the card being inproximity of a user's device, or point-of-sale terminal 290 (or the carddispenser 100), circuitry 195 may be turned on (e.g., using radiofrequency). The card may then be authenticated (e.g., via multifactorauthentication), after which the display may be turned on and the datapresented on the display.

In some embodiments, card writer 150 may be configured to render data onthe surface of the card. For example, card writer 150 may be configuredto print a portion of the card on one or more outer surfaces of thecard. Card writer 150 may use one or more card printing techniquesincluding thermal transfer using color ribbons, dye diffusion thermaltransfer, laser printing, ink jet, reverse image transfer techniques,stamping, embossing, water mark techniques, or other printing (orwriting) techniques. In some embodiments, card writer 150 may determinean appropriate technology for various data to be printed (e.g., thermalprinting issuer's name, contact info, Card Verification Value (CVV),etc.; embossing user's name, expiration date, etc.; or stamping a watermark). In some embodiments, card writer 150 may be configured tooverwrite or erase some or all previously printed information. Cardwriter 150 may be configured to determine which printed information tokeep and which information to overwrite (e.g., by comparing thepreviously printed information and the card data).

In some embodiments, card output 160 may be configured to dispense card190. Card output 160 may be operatively connected to transport assembly140, card writer 150, card feeder 110, controller 170, or othercomponents of card dispenser 100. In some embodiments, card output 160may be configured to receive card 190 after being processed by cardwriter 150. For example, card output 160 may be configured to read carddata on the card before dispensing the card. In some embodiments, cardoutput 160 may be configured to power the card 190, read the card datafrom the card 190, compare the data on the card 190 with the card datareceived by card dispenser 100 (to be written on the card 190), anddispense the card 190 responsive to the data on the card 190 matchingthe card data. In some embodiments, responsive to the data not matching,card output 160 may be configured to return the card 190 to card writer150 (e.g., for rewriting) or for discarding the card 190. Card output160 may be in the form of a slot, a tray, a tube, or receptacle fordispensing the card. In some embodiments, some or all operationsperformed by card dispenser may be performed by card feeder 110. Forexample, transport assembly 140 may be configured to transport the card190 from card writer 150 back to card feeder 110 for dispensing.

It should be appreciated that the description of the functionalityprovided by the different components of card dispenser 100 describedherein is for illustrative purposes, and is not intended to be limiting,as any of components of card dispenser 100 may provide more or lessfunctionality than described. For example, one or more of components110, 120, 140, 150, or 160 may be eliminated, and some or all of theirfunctionality may be provided by other ones of the components of carddispenser 100. As another example, additional subsystems may beconfigured to perform some, or all of the functionality attributedherein to one of the components of card dispenser 100.

In some embodiments, controller 170 may be configured to manage one ormore operations of card dispenser 100. For example, controller 170 maybe configured to transfer information, instructions, or signals tooperate components 110, 120, 140, 150, and 160. In some embodiments,controller 170 may be operatively connected to and in communication withcomponents 110, 120, 140, 150, and 160 and may include a processor,memory, storage, I/O device, or other components.

Controller 170 may be configured to provide information-processingcapabilities in card dispenser 100 for example, by executing one or moreprogram instructions to perform one or more functions of components 110,120, 140, 150, and 160. In some embodiments, controller 170 may includeone or more of a digital processor, an analog processor, a digitalcircuit designed to process information, an analog circuit designed toprocess information, a state machine, or other mechanisms forelectronically processing information. In some embodiments, controller170 may include one or more processing units. The processing units maybe physically located within the same device, or controller 170 mayrepresent processing functionality of a plurality of devices operatingin coordination. In some embodiments, controller 170 may implementvirtual machine technologies, or other known technologies to provide theability to execute, control, run, manipulate, store, etc. multiplesoftware processes, applications, programs, etc. One of ordinary skillin the art would understand that other types of processor arrangementsmay be implemented that provide for the capabilities disclosed herein.

In some embodiments, controller 170 may include one or more storagedevices configured to store information used to perform certainfunctions related to the disclosed embodiments. As an example,controller 170 may include memory that includes instructions (orprograms) that, when executed, perform one or more processes consistentwith the functionalities of components 110, 120, 140, 150, and 160. Forexample, the memory may include programs/instructions to execute one ormore applications, such as card dispenser applications, an electronictransaction application, network communication processes, and any othertype of application or software known to be available on computersystems. In some embodiments, controller 170 may execute one or moreprograms located remotely from controller 170 or card dispenser 100. Forexample, controller 170 may access one or more remote programs via acommunications network similar to network 295 (shown in FIG. 2 anddescribed herein).

FIG. 2 shows an example of a system 200 that includes card dispenser100, in accordance with one or more embodiments. In some embodiments,system 200 may include a user device 220 associated with a user,point-of-sale terminal 290 with which the user may enter into atransaction using card 190 or user device 220, server system 250, orother components. In some embodiments, system 200 may also include anetwork 295 to facilitate communication between the components of system200.

In some embodiments, user device 220 may be configured to communicatewith server system 250 and perform one or more aspects of the disclosedoperations. User device 220 may also be used for authenticating, theuser, card 190, or operations performed by one or more components ofsystem 200 (e.g., card dispenser 100, point-of-sale terminal 290, etc.).In some embodiments, user device 220 may be configured for multi-factorauthentication, proximity authentication, or other forms ofauthentication. For example, user device 220 may include anauthentication program (or application) configured authenticate theuser, the card, or a transaction. In some embodiments, user device 220may be configured to control card 190 based on proximity of the card andthe user device. For example, by sending authorize/lock/unlock, or othercontrol signals to card 190. User device 220 may authenticate theuser/card/transaction using multi-factor authentication via pushnotifications (e.g., from server system 250, point-of-sale terminal 290,card dispenser 100, or other components.) In some embodiments, userdevice 220 may be configured to communicate with server system 250 via auser application installed thereon, access to a web page, a messagingsystem, or other forms of communications. In addition, user device 220may allow the user to access information stored in server system 250,such as, for example, financial and or account information related torecent purchase transactions, financial statements, account information,rewards program information and the like.

In some embodiments, the user may operate user device 220 to control oneor more operations of card dispenser 100. For example, user device 220may be used to authenticate the identity of the user before the start ofthe operations of card dispenser 100 (via communication with serversystem 250). For example, user device 220 may be used to receive arequest for a card (e.g., from user), define card use parameters of thecard (e.g., via user input), provide card data to card dispenser 100(e.g., received from server system 250), authorize printing of the card(after verification and authentication with server system 250), orperform other operations of card dispenser 100.

In some embodiments, the user device 220 may be one or more of desktopcomputers, laptop computers, handheld computers, NetBooks, tablets,Smartphones, Smartwatches, PDAs, cellular telephones, PC's or anysuitable device with computing capability. User device 220 may includeone or more processor(s) and memory device(s) known to those skilled inthe art. For example, user device may include memory device(s) thatstore data and software instructions that, when executed by one or moreprocessor(s), perform operations consistent with one or more of thedisclosed embodiments. In some embodiments, user device may have anapplication installed thereon, which may enable user device 220 tocommunicate with Server system 250 via network 295. For instance, userdevice may be a smartphone or tablet or the like that executes a storedmobile application that performs online financial operations. In otherembodiments, user device may connect to server system 250 through use ofbrowser software stored and executed by user device.

Point-of-sale terminal 290 may be any suitable device for communicatingwith a merchant computer or payment processing network, and forinteracting with a payment device, a user computer apparatus, or a usermobile device. An access device may generally be located in any suitablelocation, such as at the location of a merchant. point-of-sale terminal290 may be in any suitable form. Some examples of point-of-sale terminal290 as used herein may include cellular phones, PDAs, personal computers(PCs), tablet PCs, hand-held specialized readers, set-top boxes,electronic cash registers (ECRs), automated teller machines (ATMs),virtual cash registers (VCRs), kiosks, security systems, access systems,Websites, and the like. point-of-sale terminal 290 may use any suitablecontact or contactless mode of operation to send or receive data from,or associated with, a portable communication device. In someembodiments, point-of-sale terminal 290 may include a reader, aprocessor, and a computer-readable medium. A reader may include anysuitable contact or contactless mode of operation. For example,exemplary card readers can include radio frequency (RF) antennas,optical scanners, bar code readers, or magnetic stripe readers tointeract with a portable communication device.

In some embodiments, server system 250 may be configured to perform oneor more operations related to the user account. For example, serversystem 250 may be configured to manage the user account. In addition,server system 250 may be configured to authorize one or more operationsof card dispenser 100. In some embodiments, server system 250 mayreceive a request (e.g., from user via the user device) for printing acard associated with the user account and authenticate the user (e.g.,via a multi-factor authentication). In some embodiments, server system250 may be configured to generate a card identifier associated with theuser account. The card identifier may be a card number (e.g., to berendered on the card). In some embodiments, the card identifier israndomly generated such that the card identifier is different from theaccount number, or different from previously generated identifiersassociated with the account. In some embodiments, the card identifiermay be chosen from a database of unique identifiers.

In some embodiments, server system 250 may be configured to generate aunique derivation key for encrypting the card identifier. For example,the card identifier encrypted using the unique derivation key may beused by the card during communications with server system 250 (orpoint-of-sale terminal 290, card dispenser 100, or other systems). Insome embodiments, the unique derivation key is derived from a master keyof the server system 250. In some embodiments, the card may beconfigured to generate a dynamic cryptogram (for a one-time use) usingthe derivation key (e.g., for each interaction with point-of-saleterminal 290). For example, server system 250 provide may provide to thecard dispenser other digital certificates, that along with the staticcryptogram, and the card's generated cryptogram may be used forencrypting communications between the card, point-of-sale terminal 290,or the server system 250.

In some embodiments, server system 250 may determine one or more carduse parameters associated with the card. For example, the card useparameters may define time, location, services, users, restrictions, orother parameters for using the card. For example, one or more useparameter determined by server system 250 may include an expirationdate, a location (e.g., a specific building, floor, garage, office, lab,etc.), a geographic area (e.g., a specific city, state, country, etc.),a type of business where the plastic is valid, or other use parameters.

In some embodiments, server system 250 may include one or more computingsystems that are configured to execute software instructions stored onone or more memory devices to perform operations consistent with thedisclosed embodiments. For example, server system 250 may include one ormore memory device(s) storing data and software instructions and one ormore processor(s) configured to use the data and execute the softwareinstructions to perform server-based functions and operations known tothose skilled in the art.

The following is an example of operations of system 200. In thisexample, the card is a transaction card, and the card issuer is afinancial institution. In some embodiments, a user may operate a userdevice 220 to print a plastic transaction card using card dispenser 100.In some embodiments, card dispenser 100 may be integrated with ATMs,placed at bank branches, or be a stand-alone dispenser. In someembodiments, the financial institution's server system 250 may generatea virtual card number (that may be referred to as a card identifier)that is linked to the user account. For example, the virtual card numbermay be linked to a transaction card of the user (e.g., credit or debitcard). In some embodiments, card dispenser 100 may be configured torender the virtual card number on the transaction card (e.g., on a carddisplay).

In some embodiments, server system 250 may provide to the card dispensercard data for the transaction card. For example, the card data mayinclude a name, a cvv number, or expiration date. In addition, userdevice 220 (e.g., via an online dashboard) may allow the user tomonitor, or control card spend activity on the account the card numberis linked to. In some embodiments, the user may define one or more useparameters for the transaction card for example by customizing the cardfor one or more authorized users, categories, merchants, locations, andspend limits (e.g., overall spend limit, spend limit per category, spendlimit per location, spend limit per merchant, etc.). This may provide aseamless integration with account holder financial institutions systems.Changes made to the transaction card may take effect immediately therebyreducing the wait time and the need for service support to link newcards to the user account. The transaction card may help mitigate fraudon lost or stolen credit cards by revealing a virtual number, cvv andexpiration date on the physical transaction card in place of thecustomer's real credit card credentials.

Network 295 may comprise any type of computer networking arrangementused to exchange data. For example, network 295 may include theInternet, a private data network, a virtual private network using apublic network, a Wi-Fi network, a LAN or WAN network, or other suitableconnections that may enable information exchange among variouscomponents of the system 200. Network 295 may also include a publicswitched telephone network (“PSTN”) or a wireless cellular network. Inother embodiments, one or more components of system 200 may communicatedirectly through a dedicated communication link(s), such as linksbetween user device 220, card dispenser 100, server system 250, terminal290, and or other components of the system.

In some embodiments, network 295 may include a direct communicationnetwork. Direct communications may use any suitable technologies,including, for example, BLUETOOTH™, BLUETOOTH LE™ (BLE), Wi-Fi, nearfield communications (NFC), or other suitable communication methods thatprovide a medium for transmitting data between separate devices. Incertain embodiments, user device 220, card dispenser 100, server system250, terminal 290, and or other components may connect and communicatethrough a direct communications network.

Example Flowchart(s)

The example flowchart(s) described herein of processing operations ofmethods that enable the various features and functionality of the systemas described in detail above. The processing operations of each methodpresented below are intended to be illustrative and non-limiting. Insome embodiments, for example, the methods may be accomplished with oneor more additional operations not described, or without one or more ofthe operations discussed. Additionally, the order in which theprocessing operations of the methods are illustrated (and describedbelow) is not intended to be limiting.

In some embodiments, the methods may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, or other mechanismsfor electronically processing information). The processing devices mayinclude one or more devices executing some or all of the operations ofthe methods in response to instructions stored electronically on anelectronic storage medium. The processing devices may include one ormore devices configured through hardware, firmware, or software to bespecifically designed for execution of one or more of the operations ofthe methods.

FIG. 3 shows a flowchart of a method 300 of dispensing a card inaccordance with one or more embodiments. At operation 302, a card (e.g.,a rewritable card or other card) may be received at an input area of acard dispenser. As an example, the input area may include a card feederor other component with an opening (or other portion) to receive thecard or to receive and dispense the card. Operation 302 may be performedby a component that is the same as or similar to card feeder 110, inaccordance with one or more embodiments.

At operation 304, card data for the card may be received. As an example,the card data may include a card identifier of a plurality of cardidentifiers associated with an account of the user, an encryption keyfor encrypting the card identifier, or other data. As a further example,the card data may include card use parameters defining one or morerestrictions or other features of the card related to usage of the card.Operation 304 may be performed by a component that is the same as orsimilar to card writer 150, in accordance with one or more embodiments.

In some embodiments, the card data may be received via a short-rangewireless connection with a user device (e.g., from an application on theuser device). As an example, proximity of the user device of the usermay be detected, and the short-range wireless connection may beestablished between the card dispenser and the user device. The carddispenser may transmit a request for the card data to the user devicevia the short-range wireless connection and, in response, receive thecard data from the user device via the short-range wireless connection.

At operation 306, at least a portion of the card data may be rendered onan outer surface of the card. As an example, the card identifier (orother portion of the card data) may be rendered using one or more cardprinting techniques, including thermal transfer using color ribbons, dyediffusion thermal transfer, laser printing, ink jet, reverse imagetransfer techniques, stamping, embossing, water mark techniques, orother printing (or writing) techniques. Operation 306 may be performedby a component that is the same as or similar to card writer 150, inaccordance with one or more embodiments.

FIG. 4 shows a flowchart of a method 400 of dispensing a card inaccordance with one or more embodiments. At operation 402, a card (e.g.,a rewritable card or other card) may be received at an input area of acard dispenser. As an example, the input area may include a card feederor other component with an opening (or other portion) to receive thecard or to receive and dispense the card. Operation 402 may be performedby a component that is the same as or similar to card feeder 110, inaccordance with one or more embodiments.

At operation 404, card data for the card may be received. As indicatedabove, the card data may include a card identifier of a plurality ofcard identifiers associated with an account of the user, an encryptionkey for encrypting the card identifier, one or more card use parameters,or other data. As an example, the card data may be received via ashort-range wireless connection with a user device of the user (e.g.,from an application on the user device). Operation 404 may be performedby a component that is the same as or similar to card writer 150, inaccordance with one or more embodiments.

At operation 406, the card data may be written or overwritten to memoryof the card, which will cause at least a portion of the card data to berendered on an outer surface of the card. As an example, the card may beprogrammed with one or more instructions to present the card dataportion that is written to a predefined memory location or data field ofthe card. As such, by writing the card data portion to the predefinedmemory location or data field, the card data portion is rendered on adisplay of the card (e.g., an electrophoretic display or other low powerdisplay). Operation 406 may be performed by a component that is the sameas or similar to card writer 150, in accordance with one or moreembodiments.

In some embodiments, the card dispenser may power the card to enablewriting to the memory of the card. As an example, the card may be apassive card, and, upon being powered, the card may begin communicatingwith the card dispenser via RFID, NFC, or other wireless techniques. Insome embodiments, where the card comprises a display, the powering ofthe card by the card dispenser may include powering of the display ofthe card to cause at least a portion of the card data written to thememory of the card (e.g., stored at a predefined memory location or datafield of the card) to be rendered on the display (e.g., anelectrophoretic display or other low power display).

FIG. 5 shows a flowchart of a method 500 of dispensing a card inaccordance with one or more embodiments. At operation 502, a card (e.g.,a rewritable card or other card) may be received at an input area of acard dispenser. As an example, the input area may include a card feederor other component with an opening (or other portion) to receive thecard or to receive and dispense the card. Operation 502 may be performedby a component that is the same as or similar to card feeder 110, inaccordance with one or more embodiments.

At operation 504, the card is transported to a writing area of the carddispenser. Operation 504 may be performed by a component that is thesame as or similar to transport assembly 140, in accordance with one ormore embodiments.

At operation 506, card data for the card may be received via ashort-range wireless connection with a mobile device of a user (e.g.,from a mobile application on the mobile device). As indicated above, thecard data may include a card identifier of a plurality of cardidentifiers associated with an account of the user, an encryption keyfor encrypting the card identifier, one or more card use parameters, orother data. As an example, proximity of the mobile device of the usermay be detected, and the short-range wireless connection may beestablished between the card dispenser and the mobile device. The carddispenser may transmit a request for the card data to the mobile devicevia the short-range wireless connection and, in response, receive thecard data from the mobile device via the short-range wirelessconnection.

At operation 508, an electrophoretic display of the card may be powered.As an example, the electrophoretic display may be wirelessly powered viaone or more wireless power transfer techniques (e.g., via inductivecoupling or other techniques). Operation 508 may be performed by acomponent that is the same as or similar to card writer 150, inaccordance with one or more embodiments.

At operation 510, a memory of the card may be written or overwrittenwith the card data to cause at least a portion of the card data to berendered on the electrophoretic display of the card. As an example, thecard may be programmed with one or more instructions to present the carddata portion that is written to a predefined memory location or datafield of the card. By writing the card data portion to the predefinedmemory location or data field, the card data portion is rendered on theelectrophoretic display. Operation 510 may be performed by a componentthat is the same as or similar to card writer 150, in accordance withone or more embodiments.

At operation 512, powering of the electrophoretic display of the cardmay be stopped such that the portion of the card data remains on theelectrophoretic display of the card subsequent to the stopping of thepowering of the electrophoretic display of the card. Operation 512 maybe performed by a component that is the same as or similar to cardwriter 150, in accordance with one or more embodiments.

In some embodiments, the various devices illustrated in FIGS. 1-2 mayinclude one or more computing devices that are programmed to perform thefunctions described herein. The computing devices may include one ormore electronic storages, one or more physical processors programmedwith one or more computer program instructions, or other components. Thecomputing devices may include communication lines or ports to enable theexchange of information within a network (e.g., network 295) or othercomputing platforms via wired or wireless techniques (e.g., Ethernet,fiber optics, coaxial cable, WiFi, Bluetooth, near field communication,or other technologies). The computing devices may include a plurality ofhardware, software, or firmware components operating together. Forexample, the computing devices may be implemented by a cloud ofcomputing platforms operating together as the computing devices.

The electronic storages may include non-transitory storage media thatelectronically stores information. The storage media of the electronicstorages may include one or both of (i) system storage that is providedintegrally (e.g., substantially non-removable) with servers or clientdevices or (ii) removable storage that is removably connectable to theservers or client devices via, for example, a port (e.g., a USB port, afirewire port, etc.) or a drive (e.g., a disk drive, etc.). Theelectronic storages may include one or more of optically readablestorage media (e.g., optical disks, etc.), magnetically readable storagemedia (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.),electrical charge-based storage media (e.g., EEPROM, RAM, etc.),solid-state storage media (e.g., flash drive, etc.), or otherelectronically readable storage media. The electronic storages mayinclude one or more virtual storage resources (e.g., cloud storage, avirtual private network, or other virtual storage resources). Theelectronic storage may store software algorithms, information determinedby the processors, information obtained from servers, informationobtained from client devices, or other information that enables thefunctionality as described herein.

The processors may be programmed to provide information processingcapabilities in the computing devices. As such, the processors mayinclude one or more of a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, or other mechanismsfor electronically processing information. In some embodiments, theprocessors may include a plurality of processing units. These processingunits may be physically located within the same device, or theprocessors may represent processing functionality of a plurality ofdevices operating in coordination. The processors may be programmed toexecute computer program instructions to perform functions describedherein. The processors may be programmed to execute computer programinstructions by software; hardware; firmware; some combination ofsoftware, hardware, or firmware; or other mechanisms for configuringprocessing capabilities on the processors.

Although the present invention has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred embodiments, it is to be understood thatsuch detail is solely for that purpose and that the invention is notlimited to the disclosed embodiments, but, on the contrary, is intendedto cover modifications and equivalent arrangements that are within thescope of the appended claims. For example, it is to be understood thatthe present invention contemplates that, to the extent possible, one ormore features of any embodiment can be combined with one or morefeatures of any other embodiment.

The present techniques will be better understood with reference to thefollowing enumerated embodiments:

-   -   1. A method comprising: receiving a card; receiving card data        for a user; and rendering at least a portion of the card data on        an outer surface of the card.    -   2. The method of embodiment 1, wherein the card data comprises        card identifier of a plurality of card identifiers associated        with an account of the user.    -   3. The method of any of embodiments 1-2, wherein the card data        comprises an encryption key for encrypting the card identifier.    -   4. The method of any of embodiments 1-3, further comprising        writing the card data on a memory of the card.    -   5. The method of any of embodiments 1-3, further comprising        overwriting the card data on a memory of the card.    -   6. The method of any of embodiments 1-5, wherein the card data        is received via a short-range wireless connection.    -   7. The method of any of embodiments 2-6, further comprising        rendering the card identifier on the outer surface of the card.    -   8. The method of any of embodiments 1-7, wherein the card data        further comprises card use parameters defining parameters of use        of the card.    -   9. The method of any of embodiments 1-8, wherein the card data        comprises a second card identifier different from the card        identifier.    -   10. The method of embodiment 9, wherein the card identifier is        associated with a first card use parameter.    -   11. The method of embodiment 10, wherein the second card        identifier is associated with a first card use parameter.    -   12. The method of any of embodiments 1-11, further comprising        powering a display of the card.    -   13. The method of embodiment 12, further comprising rendering        the at least portion of the card data on display of the card.    -   14. The method of embodiment 13, further comprising stopping the        powering of the display of the card, wherein the rendering of        the portion of the card data remains on the display of the card        subsequent to the stopping of the powering of the display of the        card.    -   15. The method of embodiments 1-14, further comprising:        detecting proximity of a user device of the user; establishing,        based on the detection, a short-range wireless connection with        the user device; and transmitting a request for the card data to        the user device via the short-range wireless connection.    -   16. A tangible, non-transitory, machine-readable media storing        instructions that, when executed by an apparatus, cause the        apparatus to effectuate operations comprising those of any of        embodiments 1-15.    -   17. A system comprising: one or more processors; and memory        storing instructions that, when executed by the processors,        cause the processors to effectuate operations comprising those        of any of embodiments 1-15.    -   18. An apparatus that performs the operations of any of        embodiments 1-15.    -   19. A card dispenser for dispensing rewritable cards, the card        dispenser comprising: a card feeder configured to receive or        dispense a rewritable card, the rewritable card comprising an        electrophoretic display; a roller assembly, within the card        dispenser, configured to move the card from the card feeder to        one or more components within the card dispenser and back to the        card feeder; a processor configured to receive card data via a        short-range wireless connection with a mobile device of a user,        the card data comprising (i) a card identifier of a plurality of        card identifiers associated with an account of the user and (ii)        a unique derivation key for encrypting the card identifier, the        unique derivation key being derived from a unique master key;        and a card writer, within the card dispenser, configured to:        power the electrophoretic display of the rewritable card;        overwrite memory of the rewritable card with the card data to        cause at least a portion of the card data to be rendered on the        electrophoretic display of the rewritable card; and stop the        powering of the electrophoretic display of the rewritable card,        wherein the rendering of the portion of the card data remains on        the electrophoretic display of the rewritable card subsequent to        the stopping of the powering of the electrophoretic display of        the rewritable card.    -   20. The card dispenser of embodiment 19, wherein causing the        portion of the card data to be rendered comprises causing the        card identifier to be rendered on the electrophoretic display of        the card.    -   21. The card dispenser of any of embodiments 19-20, wherein the        processor is configured to: detect proximity of the mobile        device of the user; establish, based on the detection, the        short-range wireless connection with the mobile device; and        transmit a request for the card data to the mobile device.    -   22. The card dispenser any of embodiments 19-21, wherein the        card data comprises card use parameters related to categories        and threshold values associated with the categories, the card        use parameters comprising a card use parameter associated with        the card identifier.

What is claimed is:
 1. A card dispenser for dispensing rewritable cards,the card dispenser comprising: a card feeder configured to receive ordispense a rewritable card, the rewritable card comprising anelectrophoretic display: a roller assembly, within the card dispenser,configured to move the rewritable card from the card feeder to one ormore components within the card dispenser and back to the card feeder; aprocessor configured to: receive card data via a short-range wirelessconnection with a mobile device of a user, the card data comprising (i)a card identifier of a plurality of card identifiers associated with anaccount of the user and (ii) a unique derivation key for encrypting thecard identifier, the unique derivation key being derived from a uniquemaster key; and determine, based on one or more parameters of theelectrophoretic display, a first portion of the card data to render onthe electrophoretic display of the rewritable card and a second portionof the card data to render on a surface of the rewritable card; and acard writer, within the card dispenser, configured to: power theelectrophoretic display of the rewritable card; cause the first portionof the card data to be rendered on the electrophoretic display of therewritable card and the second portion of the card data to be renderedon the surface of the rewritable card; and stop powering theelectrophoretic display of the rewritable card, wherein rendering thefirst portion of the card data remains on the electrophoretic display ofthe rewritable card subsequent to stopping powering of theelectrophoretic display of the rewritable card.
 2. The card dispenser ofclaim 1, wherein causing the first portion of the card data to berendered comprises causing the card identifier to be rendered on theelectrophoretic display of the rewritable card.
 3. The card dispenser ofclaim 1, wherein the processor is configured to: detect proximity of themobile device of the user; establish, based on the detection, theshort-range wireless connection with the mobile device; and transmit arequest for the card data to the mobile device.
 4. The card dispenser ofclaim 1, wherein the card data comprises card use parameters related tocategories and threshold values associated with the categories, the carduse parameters comprising a card use parameter associated with the cardidentifier.
 5. An apparatus comprising: a card receiver configured toreceive a card; a processor configured to: receive card data from a userdevice of a user over a wireless connection, the card data comprising(i) a card identifier of a plurality of card identifiers associated withan account of the user and (ii) an encryption key for encrypting thecard identifier; and determine, based on one or more parameters of anelectrophoretic display of the card, a first portion of the card data torender on the electrophoretic display of the card and a second portionof the card data to render on an outer surface of the card; and a cardwriter configured to: apply power to the card; while the power isapplied to the card, cause the first portion of the card data to berendered on the electrophoretic display and the second portion of thecard data to be rendered on the outer surface of the card; and stopapplication of the power to the card, wherein rendering of the firstportion of the card data disappears from the outer surface of the cardsubsequent to stopping powering the card and appears again when power isapplied to the card again.
 6. The apparatus of claim 5, wherein causingthe first portion of the card data to be rendered comprises causing thecard identifier to be rendered on the outer surface of the card.
 7. Theapparatus of claim 5, wherein the card writer is configured to power thecard to enable writing or overwriting of the first portion of the carddata to memory of the card.
 8. The apparatus of claim 5, wherein thecard writer is configured to power the electrophoretic display of thecard, wherein powering of the electrophoretic display of the cardenables the first portion of the card data to be rendered on theelectrophoretic display responsive to overwriting of the card data inmemory of the card.
 9. The apparatus of claim 5, wherein the card writeris configured to erase information previously rendered on the outersurface of the card.
 10. The apparatus of claim 5, wherein the card datacomprises card use parameters related to categories and threshold valuesassociated with the categories, the card use parameters comprising acard use parameter associated with the card identifier.
 11. Theapparatus of claim 5, wherein the card data comprises card useparameters related to categories and threshold values associated withthe categories, the card use parameters comprising a first card useparameter associated with the card identifier and a second card useparameter associated with a second card identifier of the plurality ofcard identifiers associated with the account of the user.
 12. Theapparatus of claim 11, wherein causing the second portion of the carddata to be rendered comprises causing the card identifier and the secondcard identifier to be rendered on the outer surface of the card.
 13. Anapparatus comprising: a card receiver configured to receive a card; aprocessor configured to: receive, over a wireless connection, card datacomprising (i) a card identifier of a plurality of card identifiersassociated with an account of a user and (ii) an encryption key forencrypting the card identifier; and determine, based on one or moreparameters of an electrophoretic display of the card, a first portion ofthe card data to render on the electrophoretic display and a secondportion of the card data to render on an outer surface of the card; anda card writer configured to: apply power to the card; while the power isapplied to the card, cause the first portion of the card data to berendered on the electrophoretic display and the second portion of thecard data on the outer surface of the card; and stop application of thepower to the card.
 14. The apparatus of claim 13, wherein causing thesecond portion of the card data, to be rendered comprises causing thecard identifier to be rendered on the outer surface of the card.
 15. Theapparatus of claim 13, wherein the card writer is configured to powerthe card and write the card data to a memory of the card when poweringof the card.
 16. The apparatus of claim 13, wherein the card writer isconfigured to power the electrophoretic display of the card, powering ofthe electrophoretic display of the card enabling the first portion ofthe card data to be rendered on the electrophoretic display responsiveto writing of the card data into memory of the card.
 17. The apparatusof claim 13, wherein the card writer is configured to erase informationpreviously rendered on the outer surface of the card.
 18. The apparatusof claim 13, wherein the card data comprises card use parameters relatedto categories and threshold values associated with the categories, thecard use parameters comprising a card use parameter associated with thecard identifier.